[Top] [Prev] [Next] [Bottom] [Contents]

Running an Application Server

You should now have an executable file in your project directory. This executable can be ran from the command line. You must specify a port when running this application server by using the -port command line option. An example of running an application server is:

tut2.exe -port 8888
This will start the tut2.CGI application server and it will listen to port 8888 for processing requests.

Once the application server is running you should be able to test your application just like a CGI application (Pressing the Test button). Note that you may have to clear your browser's cache to be sure your are running against an Application server and not a CGI.

If you need to rebuild your project after making changes you must kill the application server before re-linking and start it again after linking. You do not have to stop and start your Netscape server. You can use the Sapphire Application Manager Console (see below) to shutdown an application server gracefully.

Troubleshooting Application Server Configuration

While trying to get an application server configured you can run into some error messages. Most of these errors can be solved by simple configuration changes. Below are common error messages and solutions to fix these problems. Note that the error message may not be exactly what is shown below. The errors below will either be in the HTML browser trying to access the application server or, if using NSAPI in the error logs of the Netscape HTTP server.

Not Found

Could not read configuration file <full path to file>.

Init fn="sapphire-init" 
file="/usr/sapphire/config/apserver.txt"

The Sapphire Application Server `<server name>' was not found in the configuration file.

No response from application server

or

Cannot contact application server



[Top] [Prev] [Next] [Bottom] [Contents]

info@bluestone.com
Copyright © 1997, Bluestone. All rights reserved.